Argo Workflows
yamlで処理を記述する
全体的にUXが微妙mrsekut.icon
なんか全体的にデザインのセンスがないと感じる点がちょこちょこある
yamlで処理を記述する点
用語が分かりづらい
なので、以下の4つは必須
apiVersion
kind
metadata.name
spec
Argo Workflow用のkindには以下の様なものがある
table:_
kind
WorkflowEventBinding WorkflowEventBinding
vscodeのセットアップ
これなんでコードの部分画像やねんmrsekut.icon
code:settings.json
{
"yaml.schemas": {
}
}
これをすると補完されるっぽい
試す
8つのシナリオがある
Learn about loading and saving data in a workflow.
Using the API
Learn how to use the API for programmatic access.
Play with all the workflow examples here.
Argo Events
Learn how to integrate Argo Workflows with Argo Events
Install using Helm
Learn how how to install Argo Workflows using Helm Access the demo environment
GPT-4.icon
ClusterWorkflowTemplate
クラスタ全体で使えるワークフローテンプレート。すべての namespace で使用可能。
ワークフローの終了時（成功/失敗問わず）に必ず実行されるステップ。
Hooks
テンプレート単位で定義できる、exit, error, success などのフック処理。
Outputs
ステップやテンプレートが出力する値やアーティファクト。
Inputs
ステップやテンプレートが必要とする値やアーティファクト。
Volumes
PVCやemptyDirなど、ステップ間で共有できるボリューム。
Metadata
各オブジェクトに付加できるラベルやアノテーションなどのメタ情報。
Executor
実行エンジン（デフォルトは emissary、他に kubelet など）。
Service Account
ワークフローの実行に使われる Kubernetes のサービスアカウント。
完了後のワークフローを何時間後に削除するかなどを制御。
Workflow Archive
完了したワークフローの履歴を保存するための仕組み（PostgreSQL など）。
Workflow Status
Pending, Running, Succeeded, Failed, Error などの状態。
UI
サイドバー
https://gyazo.com/0c51477d9d4efe1bc79faf537cd3ac49
Workflows
Workflow Templates
手動でも実行できる
Cluster Workflow Templates
Cron Workflows
Event Flow
Argo Events allow you to trigger workflows, lambdas, and other actions when an event such as a webhooks, message, or a cron schedule occurs.
Event Sources
An event source defines what events can be used to trigger actions. Typical event sources are calender (to create events on schedule) GitHub or GitLab (to create events for Git pushes), or MinIO (to create events for file drops). Each event source publishes messages to the event bus so that sensors can listen for them.
Sensors
A sensor defines what actions to trigger when certain events occur. Typical events are a Git push, a file dropped into a bucket, or a message on a queue or topic. Typical triggers are start a workflow, creating a Kubernetes resource, or sending a message to another queue or topic. Each sensor listens for events from the event bus, checks to see if they're the right one, and then triggers some actions.
Workflow Event Bindings
Workflow event bindings allow you to trigger workflows when a webhook event is received. For example, start a build on a Git commit, or start a machine learning pipeline from a remote system.
Once you've created a workflow event binding, you can test it from the CLI using curl, for example:
Reports
User
API Docs
Plugins
Plugins allow you to extend Argo Workflows with custom code.
Help
https://gyazo.com/924eb5543a952f9ece63933dba20ed31
Getting Started
Quick Start
Training
Walk Through
About
Argo CLI
Hello World
Parameters
Steps
DAG
The Structure of Workflow Specs
Artifacts
Hardwired Artifacts
Scripts And Results
Output Parameters
Secrets
Volumes
Loops
Conditionals
Recursion
Retrying Failed or Errored Steps
Exit handlers
Timeouts
Annotations
Suspending
Kubernetes Resources
Daemon Containers
Sidecars
Docker-in-Docker Using Sidecars
Custom Template Variable Reference
Continuous Integration Examples
Core Concepts
Custom Resource Kinds
Template Types
Artifacts
Access Control
Features
Status
Patterns
UI Features
Debugging Tools
API
Plugins
Best Practices
Use Cases
FAQ
kubectl
IDE Set-Up
Field Reference
CLI Reference
Installation
Releases
Upgrading Guide
New features
Security
Configuration
Argo Server
Best Practices
Windows Container Support